Self-revelation aids for interfaces

ABSTRACT

Systems and/or methods are provided that facilitates revealing assistance information associated with a user interface. An interface can obtain input information related to interactions between the interface and a user. In addition, the interface can output assistance information in situ with the user interface. Further, a decision component that determines the in situ assistance information output by the interface based at least in part on the obtained input information.

CROSS REFERENCE TO RELATED APPLICATIONS

This patent application is a divisional of, and claims priority to,co-pending, commonly-owned U.S. patent application Ser. No. 12/017,114,filed on Jan. 21, 2008 and titled “SELF-REVELATION AIDS FOR INTERFACES”,the disclosure of which is incorporated herein in its entirety.

BACKGROUND

Technological advances associated with computers, operating systems andapplications have enabled users to interact with systems in a vast anddiverse amount of ways. A user interface can provide textual, graphicaland/or auditory information to the user. In addition, a user interfacecan receive and/or solicit input from the user that is utilized tocontrol or operate a computer and software executing on the computer.Typically, input can be obtained via a keyboard, mouse, track pad, trackball, digital pen, and/or touch screen. Further, user interfaces can benon-interactive such as batch interfaces wherein all input is providedup front in batch jobs. In addition, interactive user interfaces canrange from simple (e.g., command line interfaces) to complex (e.g.,graphical user interfaces). As interfaces grow in complexity, thefunctionality and features provided therein also expands.

A user often must overcome a learning curve with a user interface beforeefficient, productive utilization of the interface can occur. Moreover,for novel interfaces (e.g., gesture-based, touch-based, crossing-based,etc.), it can be even more difficult to learn and understand themechanisms employable to fully interact with the system. User interfacedocumentation can be provided in the form of help screens or usermanuals. However, such information is typically provided separate fromthe application and/or user interface such that it is difficult toperceive both simultaneously.

SUMMARY

The following discloses a simplified summary of the specification inorder to provide a basic understanding of some aspects of thespecification. This summary is not an extensive overview of thespecification. It is intended to neither identify key or criticalelements of the specification nor delineate the scope of thespecification. Its sole purpose is to disclose some concepts of thespecification in a simplified form as a prelude to the more detaileddescription that is disclosed later.

The subject innovation relates to systems and/or methods that facilitateproviding assistance information in situ with a user interface.Assistance information or tips can overlay the user interface withoutdisturbing a mode, state or responsiveness of the underlying userinterface. Thus, a user can perceive the tips that convey assistanceinformation related to features or functionality of the user interfacewithout having to leave the context of the interface. Self-revelation isutilized to allow assistance information to appear and/or disappearautomatically based on obtained input information or a context of theinterface and/or user.

In accordance with an aspect of the disclosure, a tip revelation systemis provided. The system includes a decision component that ascertainswhether to show and/or dismiss tips or tip collections based uponobtained user input and/or context information. For example, thedecision component can activate a tip related to a marking menu (i.e.,menu with options positioned at different directions relative to acentral control element) if the decision component senses that the useris hovering over the marking menu without initiating an option via adirectional gesture with an input device.

According to another aspect of the disclosure, mechanisms are providedto enable a user to explicitly show or hide tips and/or tip collections.In addition, preference data can be persisted such that particular tipswill not be revealed after a user becomes familiar with the associatedfeatures or functionality of the interface. Moreover, mechanisms areprovided to extend gesture-based input to legacy applications developedwithout gestures in mind.

The following description and the annexed drawings set forth certainillustrative aspects of the specification. These aspects are indicative,however, of but a few of the various ways in which the principles of thespecification can be employed. Other advantages and novel features ofthe specification will become apparent from the following detaileddescription of the specification when considered in conjunction with thedrawings.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a block diagram of an exemplary system thatfacilitates providing assistance information in situ with a userinterface.

FIG. 2 illustrates a block diagram of an exemplary system thatfacilitates providing in situ assistance information with a detailedinterface component in accordance with an aspect of the subjectdisclosure.

FIG. 3 illustrates a block diagram of an exemplary system thatfacilitates providing in situ assistance information with a detailedoutput component in accordance with an aspect of the subject disclosure.

FIG. 4 illustrates a block diagram of an exemplary system thatfacilitates providing in situ assistance information with a detaileddecision component in accordance with an aspect of the subjectdisclosure.

FIG. 5 illustrates a block diagram of an exemplary system thatfacilitates providing in situ assistance information with a detailedselection component in accordance with an aspect of the subjectdisclosure.

FIG. 6 illustrates an exemplary methodology for revealing tipinformation in situ with a user interface.

FIG. 7 illustrates an exemplary methodology for revealing tipinformation in situ with gesture-based marking menu in a user interface.

FIG. 8 illustrates an exemplary methodology for managing tip collectionsin accordance with an aspect of the subject disclosure.

FIG. 9 illustrates an exemplary methodology that facilitates revealingtip information for multiple overlapping gestures according to an aspectof the subject disclosure.

FIG. 10 illustrates an exemplary methodology that facilitates extendinggestures to applications in accordance with an aspect of the subjectdisclosure.

FIG. 11 illustrates an exemplary networking environment, wherein thenovel aspects of the claimed subject matter can be employed.

FIG. 12 illustrates an exemplary operating environment that can beemployed in accordance with the claimed subject matter.

DETAILED DESCRIPTION

The claimed subject matter is now described with reference to thedrawings, wherein like reference numerals are used to refer to likeelements throughout. In the following description, for purposes ofexplanation, numerous specific details are set forth in order to providea thorough understanding of the claimed subject matter. It can beevident, however, that the claimed subject matter can be practicedwithout these specific details. In other instances, well-knownstructures and devices are shown in block diagram form in order tofacilitate describing the claimed subject matter.

As used in this application, the terms “component,” “module,” “system”,“interface”, or the like are generally intended to refer to acomputer-related entity, either hardware, a combination of hardware andsoftware, software, or software in execution. For example, a componentcan be, but is not limited to being, a process running on a processor, aprocessor, an object, an executable, a thread of execution, a program,and/or a computer. By way of illustration, both an application runningon a controller and the controller can be a component. One or morecomponents can reside within a process and/or thread of execution and acomponent can be localized on one computer and/or distributed betweentwo or more computers. As another example, an interface can include I/Ocomponents as well as associated processor, application, and/or APIcomponents.

Furthermore, the claimed subject matter can be implemented as a method,apparatus, or article of manufacture using standard programming and/orengineering techniques to produce software, firmware, hardware, or anycombination thereof to control a computer to implement the disclosedsubject matter. The term “article of manufacture” as used herein isintended to encompass a computer program accessible from anycomputer-readable device, carrier, or media. For example, computerreadable media can include but are not limited to magnetic storagedevices (e.g., hard disk, floppy disk, magnetic strips . . . ), opticaldisks (e.g., compact disk (CD), digital versatile disk (DVD) . . . ),smart cards, and flash memory devices (e.g., card, stick, key drive . .. ). Additionally it should be appreciated that a carrier wave can beemployed to carry computer-readable electronic data such as those usedin transmitting and receiving electronic mail or in accessing a networksuch as the Internet or a local area network (LAN). Of course, thoseskilled in the art will recognize many modifications can be made to thisconfiguration without departing from the scope or spirit of the claimedsubject matter.

Moreover, the word “exemplary” is used herein to mean serving as anexample, instance, or illustration. Any aspect or design describedherein as “exemplary” is not necessarily to be construed as preferred oradvantageous over other aspects or designs. Rather, use of the wordexemplary is intended to disclose concepts in a concrete fashion. Asused in this application, the term “or” is intended to mean an inclusive“or” rather than an exclusive “or”. That is, unless specified otherwise,or clear from context, “X employs A or B” is intended to mean any of thenatural inclusive permutations. That is, if X employs A; X employs B; orX employs both A and B, then “X employs A or B” is satisfied under anyof the foregoing instances. In addition, the articles “a” and “an” asused in this application and the appended claims should generally beconstrued to mean “one or more” unless specified otherwise or clear fromcontext to be directed to a singular form.

Now turning to the figures, FIG. 1 illustrates a system 100 thatfacilitates self-revelation of help information or aides related to auser interface. The help information can be tips associated with aspectsof the user interface to explain, demonstrate or otherwise inform a userof the functionality provided. The system 100 includes an interfacecomponent 102 that obtains input information and outputs assistanceinformation based at least in part on the obtained input information. Inone embodiment, the interface component 102 generates and displays agraphical user interface. The input information can be, for example,interactions of a user with the interface component 102 via an inputdevice (not shown) such as, but not limited to, a tablet and pen, atouch screen, a mouse, a touch pad, a track ball, and/or any othersuitable device capable of receiving and/or soliciting user interactionwith respect to an interface. The assistance information can relate tofunctionality of the interface component 102 revealed in such a way toenable a user to easily discover and employ various functional featuresvia the input device. For example, the assistance information can be agraphical overlay on the user interface that is displayed associatedwith at least a portion of the interface indicating techniquesemployable with the portion. In addition, the assistance information canbe displayed in situ with the user interface. In an embodiment, the insitu assistance information is rendered in a manner distinct from theunderlying user interface to highlight the assistance information asbeing separate from the user interface. Furthermore such assistance maybe rendered in a manner that intuitively suggests to the user that theassistance information consists of illustrative annotations, rather thangraphical controls (“widgets”) that are meant to be tapped or otherwiseoperated directly.

Pursuant to an illustration, the interface component 102 can be agesture-based interface such as, for example, a pen and tabletinterface. It is to be appreciated and understood that gestures can bemovements associated with commands. Moreover, gestures can be movementsthat require a user to provide a motion with an input device to activatethe associated commands. By way of example, in a gesture-basedinterface, a user can initiate a scrolling action by motioning the inputdevice in a circular or spiral pattern. In an embodiment, a gesture canbe characterized by a variety of parameters such as, but not limited to,a gesture start point, an end point, a track line (e.g., the path of thegesture movement), a speed of motion and/or any other parameters capableof distinguishing one gesture from another gesture. It is to also beappreciated that gestures can be employed in conjunction with aplurality of interfaces and input devices. For example, a mouse-basedinterface can be employed wherein a user motions the mouse cursor inaccordance with a gesture to initiate a command. Further, the interfacecomponent 102 includes mechanisms to integrate in situ assistanceinformation into virtually any application wherein assistanceinformation can enable a user to discover, learn and employ features ofthe application user interface.

The system 100 can also include a decision component 104 that determinesthe in situ assistance information output by the interface component102. The decision component 104 analyzes the input information obtainedby the interface component 102 to evaluate whether to display a tipand/or a collection of tips in situ with the user interface. Inaddition, the decision component 104 takes into account contextinformation such as a state of underlying interface elements (e.g., userinterface controls), screen dialogs currently in use, a current mode ofthe interface, a state of the user and/or any other information suitablefor a determination of whether to reveal tips. For example, a user,utilizing an input device, can hover in proximity to a particularinterface element. From the hovering, the decision component 104 caninfer that the user is unsure how to activate a desired feature.Accordingly, the decision component 104 can determine that a tipassociated with the particular interface elements should be displayed tothe user in situ with the interface element. Moreover, the decisioncomponent 104 can ascertain whether currently displayed tips and/or tipcollections should be dismissed or hidden based upon consideration ofthe input information and/or context information. The decision component104 can establish if tips and/or tip collections require adjusting orrearranging is response to a user moving and/or resizing underlying userinterface elements.

FIG. 2 illustrates a system 200 that facilitates providing in situ tipsassociated with a user interface. The system 200 can include thedecision component 104 that determines whether tips and/or tipcollections should be displayed in situ with a user interface providedby interface component 102. In addition, the decision component 104 canestablish which tips, tip collections, and/or tips within a tipcollection should be revealed based upon the input information, contextinformation, and/or history information associated with a user.Furthermore decision component 104 may employ information about theconstraints of the device's screen size such that some tips are elided,modified, or show in different relative locations to accommodate smallscreen devices. The decision component also takes into account eventssuch as moving or resizing the underlying applications, or changing thescreen orientation, to correctly display in situ tips.

The interface component 102 can include an input component 202 thatcollects input information from a user (not shown). In addition, theinterface component 102 can include user interface (UI) controls 204.The input component 202 can employ one or more controls among UIcontrols 204 to gather, solicit and/or receive input information from auser. UI controls 204 are interface elements utilized by a user tointeract with a computing environment. UI controls 204 can includegraphical objects such as, but not limited to, a button, a check box, atext box, a text label, a slider, a list box, a spinner, a drop-downlist, a menu, a toolbar, a toolbar icon, a ribbon, a combo box (i.e., atext box with attached menu or list box), an icon, a tree view, a gridview, a tab, a scrollbar, a status bar, a progress bar and/or any otherelement capable of facilitating user interaction. In addition, UIcontrols 204 can include interface elements that are collections ofother interface elements. For example, UI controls 204 can includewindows, dialog boxes, palette windows, drawers, heads-up displays andthe like. UI controls 204 are employed to generate a graphical userinterface (GUI) provided by the interface component 102.

The interface component can also include a tip component 206 thatprovides tips or assistance information associated with UI controls 204.Tip component 206 can include tips and/or tip collections associatedwith UI controls of the GUI. The tips and/or tip collections revealassistance information that indicate, demonstrate and/or exposefunctionality of UI controls 204. The tips provided by tip component 206can be overlaid on the underlying GUI. In an embodiment, the tips can betransparent or partially translucent to enable a user to see theunderlying GUI. Further, the tips can be opaque. In addition, the tipsof tip component 206 can present tips in accordance with a styledistinct from UI controls 204 so that the tips can be easilydistinguished from the underlying interface while also enabling the tipsto be displayed in situ with the UI controls 204. For example, the tipscan include different color schemes, different typefaces, etc. thanemployed in the GUI. In an embodiment, exemplar gestural strokes anddescriptions of those gestures can be presented in an informalhandwritten annotation style with yellow highlighting (similar tomarked-up corrections or comments on a real physical document), suchthat users intuitively understand the tips to be informative annotationsof the underlying interface.

The interface component 102 can also include an output component 208that coordinates construction, generation and/or maintenance of the GUI.The output component 208 can render UI controls 204 to a display orother output device (not shown). In addition, the output component 208can present tips and/or tip collections supplied from tip component 206in situ with UI controls 204 rendered on the output device. The outputcomponent 208 reveals tips based at least in part upon determinationsmade by the decision component 104. For example, the decision componentcan ascertain to show only a tip overlay associated with a particularmarking menu or gesture-based menu. Accordingly, output component 208renders the appropriate tip overlay from tip component 206 inconjunction with the marking menu control of UI controls 204.

FIG. 3 illustrates a system 300 that facilitates revealing tip orassistance information associated with a user interface in situ withcontrols of the user interface. The system 300 can include the interfacecomponent 102 that obtains input information and outputs in situassistance information based at least in part on the obtained inputinformation. In addition, the system 300 can include a decisioncomponent 104 that determines in situ assistance information output bythe interface component 102.

The interface component 102 can include an output component 208generates a GUI for an operating system and/or an application. In anembodiment, the GUI can include UI controls or interface elements aswell tips that convey assistance information. The output component 208includes a placement component 302 that ascertains placement of a UIcontrol and/or an associated tip(s) relative to other elements of theGUI. The placement component 302 facilitates organizing UI controlsand/or tip(s) on an output device such that occlusion of underlyinginterface elements is reduced or prevented. For example, it can beundesirable to have a tip masking an unrelated portion of the userinterface and/or other tips. In an embodiment, the output component 208can also include a render component 304. The render component 304 drawsor generates a graphical image and/or portion of image to be displayedon an output device (not shown). The render component 304 can producetwo-dimensional or three-dimensional representations of the UI controls204 and tips for disclosure on the output device. The render component304 can produce a final screen image in accordance with the placementinformation provided by the placement component 302. Render component304 may employ window transparency, per-pixel alpha transparency, screendoor transparency, color-key transparency, and/or nonrectangular windowregions that conform to the outline of the tips so as to present aconvincing illusion of an overlay tip window that appears in situ withother application content. In other embodiments, tips may be drawndirectly in-situ by the host application such that overlay windows arenot needed.

In addition, the output component 208 can include a fade component 306that can provide fading aspects to a UI control, tip, or other portionof the interface. A fade can be a transition from an opaque state to anon-visible state that traverses varying degrees of translucency andvice-versa. For example, the fade component 306 can enable an interfaceelement to fade into visibility, fade out of visibility, explode andfade out (e.g. a rapid progression to opacity followed by a fade out),or a combination thereof (e.g., fade out subsequent to a fade in).Furthermore, fading may be spatially correlated with the position of theinput device or screen cursor, such that tips fade out in proportion tothe distance of the pointer from an interface control. Moreover, theoutput component 208 can include an expansion component 308 thatfacilitates expanding and contracting a UI control, tip, tip collectionor other portion of the interface out of and into a particular interfaceelement. For example, the expansion component 308 enables a user todismiss a collection of tips such that the displayed tip collectionprogressively contracts or shrinks into another UI control or portion ofthe interface that can be utilized to show the tip collection at a latertime. Upon reactivation or showing, the tip collection can progressivelyexpand or grow out of the interface element employed to activate thetips.

Moreover, the output component 208 can include an animation component308. The animation component 308 can provide video or animations tovarious controls or components within a GUI. In an illustrative instanceof a gesture-based interface, the animation component 308 can provideanimations to a tip overlay that demonstrate a gesture motion or gesturesequence required to activate the feature associated with the tipoverlay. The animation component 308 can facilitate user understandingof a gesture that can involve a complex motion or sequence by exhibitingthe motion and/or sequence via animation.

Referring to FIG. 4, illustrated is a system 400 that facilitatesdeciding whether assistance information should be conveyed to a user.The system 400 includes an interface component 102 that provides a GUI.The GUI provided by the interface component 102 collects inputinformation from user via an input device (not shown). In addition, theinterface component 102 provides assistance information related toemploying features of the GUI. The assistance information can beconveyed as tips overlaid in situ with interactive elements or controlsof the GUI. The system 400 can also include a decision component 104that determines the assistance information conveyed to the user via theinterface component 102 based at least in part on consideration of theinput information or context information obtained from the interfacecomponent 102. In addition, the decision component 104 can alsoascertain if the user requires assistance information by eitherinference or direct request from the user. For example, the system maydecide to present tips if the user taps on an interface control thatresponds to stroke-based gestures, since this indicates that the usermay not be aware of the gesture functionality.

The decision component 104 can include an analysis component 402 thatevaluates input information and context information to produce relevantresults. Context information can include such information as a state ofunderlying interface elements (e.g., user interface controls), screendialogs currently in use, a current mode of the interface, a state ofthe user, user preference persisted in a data store (e.g., the systemregistry, or settings saved with an individual document) and/or anyother information suitable for determining whether to reveal tips. Inaddition, input information can include data provided by a user, userinteractions with the interface, and the like. Pursuant to anillustration, the analysis component 402 can obtain context informationindicating a user is employing a digital notebook application with apen-based input device. In addition, the analysis component 402 canevaluate input information obtained by the interface component 102reflecting that the user is focusing on an icon, tool button orgraphical portion such as a pen tool button employable to select variousink styles for pen-based input. The input information can indicate thatthe user is hovering over the pen tool button for a period withoutfurther interaction. Accordingly, the analysis component 104 canevaluate that the user is unsure of the appropriate gesture required toselect a particular ink style.

In addition, the decision component 104 includes a selection component404 that ascertains whether assistance information such as a tip overlayis to be conveyed to the user. The selection component 404 bases thedetermination at least in part on the evaluation provided by theanalysis component 402. Moreover, the selection component 404 choosesthe type of assistance information. For example, the selection component404 can choose a tip collection associated with a search panel whereinthe tip collection includes a plurality of tips showing the interactionsrequired by a user to initiate various functional aspects of the searchpanel. In an embodiment, the decision component 104 can include aresolution component 406 that can be utilized by the analysis component402 and the selection component 404 to resolve conflicts in the inputinformation, context information or both. For example, a preference canbe retained by a data store that indicates a user does not wish to seeany assistance information associated with a search panel. A user candecide to hide search panel tips after the user gains sufficientfamiliarity with the gestures. However, the interface component 102 canobtain input information signifying that the user is hovering over anelement of the search panel. The resolution component 406 can settle theapparent conflict by suggesting a subset of the tip collectionassociated with the search panel and, in particular, the subset caninclude tips relevant to the portion of the search panel occupying theuser's focus.

Various inferences or determinations that occur in relation to thedecision component 104 can be processed by an intelligence component408. For instance, the intelligence component 408 can infer that a userrequires a refresh of available interface gestures as the user has notinteracted with a particular aspect for a period of time. Moreover, theartificial intelligence component 408 can make different determinations,such as determining an appropriate tip collection to display.

The intelligence component 408 can employ one of numerous methodologiesfor learning from data and then drawing inferences and/or makingdeterminations related to applying a service (e.g., Hidden Markov Models(HMMs) and related prototypical dependency models, more generalprobabilistic graphical models, such as Bayesian networks, e.g., createdby structure search using a Bayesian model score or approximation,linear classifiers, such as support vector machines (SVMs), non-linearclassifiers, such as methods referred to as “neural network”methodologies, fuzzy logic methodologies, and other approaches thatperform data fusion, etc.) in accordance with implementing variousautomated aspects described herein. Methods also include methods for thecapture of logical relationships such as theorem provers or moreheuristic rule-based expert systems.

Turning to FIG. 5, an example system 500 is depicted that facilitatesselection and display of assistance information associated with a GUIwith an expanded decision component 104 and selection component 404. Thesystem 500 can include the interface component 102 that obtains inputinformation and outputs in situ assistance information based at least inpart on the obtained input information. In addition, the decisioncomponent 104 can determine the in situ assistance information output bythe interface component 102. The decision component 104 can include theselection component 404 that ascertains whether assistance informationsuch as a tip overlay is to be conveyed to the user.

The selection component 404 can include a proximity component 502 thatdetermines whether hover-based assistance information should bedisplayed. Pursuant to an illustration, the proximity component 502 canbe utilized to decide displaying assistance information in gesture basedinterfaces. For example, marking menus are an established pen-inputtechnique in gesture based interfaces. Marking menus offer menu commandsnot in list form as conventional menus do, but rather the menu commandsare placed in different directions (e.g., cardinal compass directions)around a central interface element or control. A gesture, such asstroking or flicking, towards the desired command selects it. Withmarking menus, a user must remember which direction to gesture in orderto activate a corresponding command. Once the layout becomes familiar,marking menus provide fast interactions, particularly with pen input.However, in early learning stages or after long periods of disuse, theuser can require reminding of the commands.

In an embodiment, a transient semi-transparent overlay can be providedas an effective hover tip over UI controls such as marking menus. It isto be appreciated that translucent overlay hover tips can be employedwith other UI controls in addition to marking menus. For example, hovertips can be utilized in connection with buttons, menus, embeddable icons(e.g., links to files, web pages, persistent representations of savedqueries, etc.), contextual menus that act on zero or more objects in acurrent selection, and the like. According to an embodiment, the hovertip overlay is a translucent surround about the central element of amarking menu wherein the tip information that indicates the commandsassociated with a given gesture direction is displayed on top of thesurround.

The proximity component 502 can ascertain when the hover tip overlay andsurround should appear based upon the user hovering an input device overthe control associated with the tip. The translucent surround featureserves several purposes. For example, the surround separates theforeground menu layer from the background UI and/or content layers. Itis to be appreciated that the surround may be omitted, but this cancause greater interference between the layers and/or decrease theutility of the tip information by reducing the ease at which it can beperceived. In addition, the translucency of the surround indicates thatthe tip information is transient and not directly actionable orinteractive. Moreover, the translucent surround hover tip maintains thecontext of the original menu (prior to tip revelation) so the userremains oriented. In addition, the surround clearly indicates to theuser where the tip came from and maintains visibility of other nearbyoptions if the user wishes to motion the input device to hover overthose options (i.e., nearby marking menu controls can be perceivedthrough the translucent surround). This makes it possible for the userto serially inquire each of a series of marking menus by hovering theinput device over each one in turn. In an embodiment, labels of the tiprepresenting the commands of the marking menu can be rendered opaquewhile only the surround remains translucent so as to increase contrastbetween the gesture commands the background layer.

In another example, the hover tip integrates additional contextualinformation, such as, but not limited to, file names, web page titles,thumbnails, universal resource locators for embedded documents and/orweb pages or the like. Further, in an illustrative instance of apen-based input with a digital notebook application, the contextualinformation can include recognized handwriting corresponding to inkassociated with a UI control. The added context information can bepositioned relative to the hover tip to avoid overlap with any of theavailable gestural commands. In addition, depending on the closeness ofa viewable area edge, the location of the contextual information can bemoved to a different position that will remain visible.

Pursuant to the marking menu illustration, the interface component 102and proximity component 502 perform several elements of hover-based tipactivation that can improve usefulness of the tips and, accordingly, theuser's ability to perceive and learn the assistance information conveyedtherein. For example, the interface component 102 can transform a cursoror other mechanism operable to signify a position on a display. Theinterface component 102 transforms a state, shape or graphical form ofthe cursor as it moves over a UI control associated with a marking menuto indicate that a gesture commands are available relative to the UIcontrol. It is to be appreciated that other transformations arepossible. For example, the cursor can transform to signify theavailability of dragging gestures. Moreover, the proximity component 502can determine, based upon the input information, whether a duration ofhover perceived is sufficient to trigger revelation of a hover-basedtip. For example, the hover tip can appear after the input device hoversabove the marking menu for a time-out period to prevent hover tips fromspuriously appearing as the user motions around the interface. In anembodiment, the time-out period can be 500 to 1000 milliseconds induration. In addition, the time-out period can shorten after a firsthover tip activates to enable a user to quickly browse hover tips for agroup of marking menus. Moreover, it is to be appreciated that otherinput information beyond hover time can be consider in deciding whetherto reveal hover tips. For example, hover tips can be activatedregardless of hover time if the user motions the input device at avelocity under a threshold. In such a case, it can be inferred that theuser is slowly roaming the interface in search of a particular feature.

The proximity component 502 can also determine whether to dismiss arevealed hover tip. In an embodiment, the hover tip can be dismissedonce the user hovers off the central UI control associated with thehover tip surround. In addition, for pen-based input devices, theproximity component 502 can hold the hover tip on the display for a fewseconds, or indefinitely if desired, despite registering an out-of-rangeevent indicating the user has pulled the pen away from the tablet ortouch screen. For pen-based gesture input on a display tablet, the penand the user's hand occludes a portion of the screen. A user canwithdraw from the screen in order to observe the hover tip withoutobstruction and the proximity component 502 does not immediately dismissthe hover tip. On devices without an out-of-range and/or hovercapability (e.g. touch-sensitive Ultra Mobile Personal Computers(UMPC's), or if out-of-range events cannot be reported to userapplications by the device driver or operating system, the system mayobserve when the cursor remains completely motionless and use this toinfer that a pointing device has been withdrawn from the screen surface.

It is to be appreciated that the proximity component 502 can providehover tip determinations to other UI controls beyond marking menus. Forexample, hover tips can be employed in conjunction with tab controlsrepresenting pages of a document. When a user hovers over the tabcontrols and a lingers for a time-out period, a hover tip explaininggestures associated with the tab controls can be revealed. For instance,the hover tip can convey a gesture that demonstrates that pages can berearranged by dragging the tab controls via an input device. In anotherembodiment, a thumbnail image of a page contents can be shown when auser hovers of a corresponding page tab.

According to another embodiment, selection component 404 can employ acollection component 504 to determine if a tip collection should berevealed. In situations, assistance information or tips do not exist inisolation but can form a tip collection providing assistance informationillustrating principal interactive behavior of a functional element orarea of the user interface. For example, a tip collection can conveyassistance information in the form of in situ tips for an entire dialogbox of the user interface. Tip collections enable a user to view avariety of gestures available in a functional area of the userinterface, discover UI elements that can be used together, and/orextrapolate how one or more gestures can be combined and/or selected toachieve a desired goal. While tips are visible, the underlying UIremains active and capable of interaction. Accordingly, a user canperceive assistance information while continuing to work.

The collection component 504 analyzes the input information obtained bythe interface component 102 to evaluate whether to display a tip and/ora collection of tips in situ with the user interface provided byinterface component 102. In addition, the collection component 504 takesinto account context information such as a state of underlying interfaceelements (e.g., user interface controls), screen dialogs currently inuse, a current mode of the interface, a state of the user and/or anyother information suitable for a determination of whether to revealtips. The collection component 504 can ascertain whether to dismiss someor all of the tips currently revealed.

In an embodiment, the collection component 504 can hide or reveal tipsbased on an explicit request from a user. For example, mechanisms can beprovided to a user to hide tips or a subset of tips and/or show tips ora subset of tips. A hide tips UI control can be provided in associationwith a tip collection displayed. The user can interact with the hidetips UI control to dismiss the tip collection currently visible. It isto be appreciated that more than one hide tips UI control can beemployed. For example, a plurality of controls can be associated withdifferent portions or subsets of visible tips. Further, each individualtip can be associated with a control by which to dismiss the tip.Moreover, a UI control can be provided to explicitly recall or showtips. Once the control is activated, the collection component 504 candetermine what tips are to be shown. In addition, separate elements ofthe user interface can include an exclusive show tips control forenabling tips on the separate element alone. The interface component 102can employ animations when hiding and showing tips in accordance withdeterminations made by the decision component 104. For example, a tipcollection can be animated to emerge and expand from a particular UIcontrol a user can employ to explicitly activate the tip collection. Inaddition, the tip collection can be animated to shrink or contract intothe UI control upon dismissal to inform a user of the control necessaryto reactive the tips.

The collection component 504 and decision component 104 can communicatewith a data store 508 to persist user preferences with regard to tipsand/or tip collections. A control can be provided along with a tipcollection to enable a user to choose to suppress the tip collectiononce a user gains familiarity with the underlying UI functionality. Auser can employ the control to indicate that the tip collection shouldnot appear again even in situations in which the decision component 104would determine revelation is appropriate. The preference can bepersisted in data store 508. The collection component 504 queries datastore 508 to discover if a preference is retained and suppresses a tipcollection accordingly. The preference can be persisted acrossapplication instances, persisted across the operating system, associatedwith a particular user or a particular file, etc.

It is to be appreciated that the data store 508 can be, for example,either volatile memory or nonvolatile memory, or can include bothvolatile and nonvolatile memory. By way of illustration, and notlimitation, nonvolatile memory can include read only memory (ROM),programmable ROM (PROM), electrically programmable ROM (EPROM),electrically erasable programmable ROM (EEPROM), or flash memory.Volatile memory can include random access memory (RAM), which acts asexternal cache memory. By way of illustration and not limitation, RAM isavailable in many forms such as static RAM (SRAM), dynamic RAM (DRAM),synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhancedSDRAM (ESDRAM), Synchlink DRAM (SLDRAM), Rambus direct RAM (RDRAM),direct Rambus dynamic RAM (DRDRAM), and Rambus dynamic RAM (RDRAM). Thedata store 508 of the subject systems and methods is intended tocomprise, without being limited to, these and any other suitable typesof memory. In addition, it is to be appreciated that the data store 508can be a server, a database, a hard drive, a pen drive, an external harddrive, a portable hard drive, and the like.

In an embodiment, the proximity component 502 and/or the collectioncomponent 504 can determine to reveal a tip and/or tip collection.Numerous gesture commands can be available to a user relative to asingle region of the user interface. In some situations, gesturescommands can be defined to avoid spatial overlap. However, even in suchsituations, numerous tips can overlap each other. The decision component104 can include a contention component 506 to resolve multipleoverlapping gestures on a given area of the interface. In anillustrative instance, when a user selects a lasso selection tool in adigital notebook application, tips can be revealed in situ thatdemonstrate various functional aspects of the lasso selection tool,including gestures employable via an input device to active respectivefunctional aspects. The revealed tips can be a collection of commonlyutilized aspects, for example. The tips can be hierarchically organizedto signify dependencies. For example, a gesture employable to drag aselection is dependent upon a selection being made. Thus, the draggesture tip can be shown dependent upon a gesture employable to selectan object, portion of content, etc. In addition, the subset of tipsdisplayed can be only those with preconditions satisfied. The revealedtips can be static representations of the respective gestures, or theymay contain images of or be drawn in reference to the current contentand objects in a user's document. In addition, the revealed tips can bevideos and/or animations of the gestures being drawn.

FIGS. 6-10 illustrate methodologies and/or flow diagrams in accordancewith the claimed subject matter. For purposes of simplicity ofexplanation, methodologies that can be implemented in accordance withthe disclosed subject matter were shown and described as a series ofblocks. However, it is to be understood and appreciated that the claimedsubject matter is not limited by the order of the blocks, as some blockscan occur in different orders and/or concurrently with other blocks fromwhat is depicted and described herein. Moreover, not all illustratedblocks can be required to implement the methodologies describedhereinafter. Additionally, it should be further appreciated that themethodologies disclosed throughout this specification are capable ofbeing stored on an article of manufacture to facilitate transporting andtransferring such methodologies to computers. The term article ofmanufacture, as used, is intended to encompass a computer programaccessible from any computer-readable device, carrier, or media.

FIG. 6 illustrates a method 600 that facilitates providing assistanceinformation in situ with a user interface. The method 600 commences atreference numeral 602 where input information and/or context informationis obtained. The input information can include information regardinginteractions of a user with the user interface. The context informationcan include a state of underlying interface elements (e.g., userinterface controls), screen dialogs currently in use, a current mode ofthe interface, a state of the user and/or any other information suitablefor a determination of whether to reveal tips. At reference numeral 604,the input information and/or context information is analyzed to evaluateor infer a state of the user with respect to the user interface. Forexample, it can ascertained based upon the input information and/orcontext information that the user is unsure what interactions arerequired to bring about particular functionality of an application. Atreference numeral 606, candidate tip information is selected. Thecandidate tip information can be determined based at least in part onthe analysis of the input and/or context information. For example, theinput information can indicate that a user is hovering over a markingmenu UI control. The candidate tip information can include a hover tipconveying available gesture commands associated with the UI control. Atreference numeral 608, the candidate tip information is revealed in situwith the interface. Pursuant to an example, the tip information can berevealed as an overlay to the associated UI control.

FIG. 7 illustrates an example method 700 that facilitates employing insitu assistance information in connection with gesture-based interfaces.The method 700 can be employed with a user interface to aid users withlearning and/or remembering functional aspects of the interface. Forexample, the method 700 can be utilized to provide in situ interfacetips associated with marking menus. Marking menus are an establishedpen-input technique in gesture-based interfaces. Marking menus offermenu commands not in list form as conventional menus do, but rather themenu commands are placed in different directions (e.g., cardinal compassdirections) around a central interface element or control. A gesture,such as stroking or flicking, towards the desired command selects it.

The method 700 commences at reference numeral 702 where proximityinformation is collected. Proximity information can include, forexample, indications that a user is maintaining proximity to a markingmenu central control via an input device. For example, with pen-basedgesture interfaces, the user can hover the pen over the marking menucontrol. At reference numeral 704, tip information is revealed inresponse to the proximity information. In an illustrative instance, thetip information can include a translucent in situ overlay providing anexplanation of the gesture commands employable with the marking menucontrol. At reference numeral 706, additional input information isobtained. At reference numeral 708, a determination is made as towhether the input information obtained indicates a tap down. A tap downevent may register if a user touches the central control of marking menuwith an input device for a given period of time (e.g., a third of asecond). If the input information is a tap down event, the methodproceeds with reference numeral 710 where the tip information cansolidify from translucent to opaque.

If No, the method proceeds to reference numeral 712 where adetermination is made as to whether the input information indicates ahover away event. For example, a user can hover outside the centralcontrol element of a marking menu to achieve a hover away event. If Yes,the tip information is hidden at reference numeral 714. In anembodiment, the tip hide on hover away discourages the user fromselecting the displayed commands with the input device rather thanperform the associated gesture. In another embodiment, the user mayhover to the desired function and then tap on the hover overlay itselfas an alternative to employing the actual gesture to activate thecommand. If No, the method proceeds to reference numeral 716.

At reference numeral 716, a determination is made as to whether theinput information signifies a hover off. In an illustrative instance ofpen-based input, a user's hand occludes a portion of the screen. Thus,the user can remove the pen from the screen in order to view thedisplayed tip information. This can trigger a hover off event. If theinput information indicates a hover off event, the method proceeds toreference numeral 718 where the revealed tip information holds on thedisplay to enable a user to perceive it. If the input is not a hover offevent, the method proceeds to reference numeral 720. At 720, it isascertained if the input information indicates marking input or agesture. If Yes, the method proceeds to reference numeral 722 where thecommand on the tip information selected by the marking input ishighlighted. For example, the selected command can explode and fade. Inanother embodiment, the command can just appear with a subsequent fade.In addition, the command can appear and then vanish after a specifiedtime (e.g., 1 second). If the input information is not marking input,the method proceeds back to reference numeral 706 where additional inputinformation is collected.

FIG. 8 illustrates a method 800 that facilitates managing tipcollections in situ with a user interface. In situations, assistanceinformation or tips do not exist in isolation but can form a tipcollection providing assistance information illustrating principalinteractive behavior of a functional element or area of the userinterface. For example, a tip collection can convey assistanceinformation in the form of in situ tips for an entire dialog box of theuser interface. Tip collections enable a user to view a variety ofgestures available in a functional area of the user interface, discoverUI elements that can be used together, and/or extrapolate how one ormore gestures can be combined and/or selected to achieve a desired goal.At reference numeral 802, a tip collection is revealed. At referencenumeral 804, input information is collected. At 806, a determination ismade as to whether the input information relates to showing or hidingtips. For example, a user can hover over a control associated with hovertips. The hover action can trigger additional tips. In addition, a usercan explicitly show or hide tips and/or tip collections. If the inputinformation indicates show, the method proceeds to reference numeral 808where additional tips are revealed in accordance the input information.At 810, background tips previously revealed are dimmed (or removedcompletely) so as to not interfere with user perception of theadditional tips. If hide was signified from the input information, therevealed tip collection is dismissed at reference numeral 812. At 814,the hidden status is retained such the tip collection does not revealagain unless explicitly requested by a user.

Turning now to FIG. 9, a method 900 is illustrated that facilitatesproviding assistance information for multiple overlapping gesture inputsin a gesture-based user interface. A variety of gestures can beemployable from a given area of the user interface. The gestures canspatially overlap such that it becomes difficult to display in situ tipinformation. The method 900 commences at reference numeral 902 where aneed to reveal tip information is identified. For example, a user mayhover over a portion of the user interface actionable with gestures. Inaddition, a need can be identified when a user activates an aspect of anapplication for the first time. At reference numeral 904, a tipcollection is identified. For example, in the case of a single hovercontrol, the tip collection can include a hover overlay for thatcontrol. In addition, a plurality of tip can be selected when a dialogis activated in the user interface. Moreover, a tip collection includingexemplary or common gestures can be selected. At reference numeral 906,a disclosure mechanism is selected. For example, a series of framesincluding static representations of multiple overlapping gestures can beemployed. In addition, the tips can be videos or animations of thegestures being drawn. At reference numeral 908, the selected tipcollection is communicated in accordance the determined disclosuremechanism.

FIG. 10 illustrates an example method 1000 that facilitates extendinggesture input to preexisting applications. For example, someapplications, such as a digital notebook application, fully employgestures. However, some applications do not employ any gestures bydefault. At reference numeral 1002, a floating tool palette isassociated with an application. In an illustrative instance, thefloating tool palette can be a translucent overlay placed in aconspicuous location on the associated application or window. Inaddition, the floating tool palette can solidify (e.g., becomes opaque)as a user hovers over the palette. At reference numeral 1004, inputentered via the palette is captured. For example, a user can activatethe palette control and initiate a gesture. In the case of pen-basedinput, a user can touch the pen down on to the palette to initiate agesture. As long as the gesture initiates within the tool palette, thegesture motion can escape the bounds of the tool palette and the inputis still captured. At reference numeral 1006, event data is generatedfrom the gesture information. For example, if a gesture is a scrollinggesture, scrolling event data is generated. At reference numeral 1008,the generated event data is forwarded to the associated application.Thus, the gesture motion performs an input operation on a user interfacenot originally implemented with gesture-based commands. This shows howan overlay can be used not only to reveal gesture functionality, butalso to directly support gesture functionality on top of applicationsthat normally would not implement such gestures. It also shows howgestural tips may themselves offer interactive feedback in response touser movement of a pointing device, rather than providing justinformation displays.

In order to provide a context for the various aspects of the disclosedsubject matter, FIGS. 11 and 12 as well as the following discussion areintended to provide a brief, general description of a suitableenvironment in which the various aspects of the disclosed subject mattercan be implemented. While the subject matter has been described above inthe general context of computer-executable instructions of a programthat runs on one or more computers, those skilled in the art willrecognize that the subject matter described herein also can beimplemented in combination with other program modules. Generally,program modules include routines, programs, components, data structures,etc. that perform particular tasks and/or implement particular abstractdata types. Moreover, those skilled in the art will appreciate that theinventive methods can be practiced with other computer systemconfigurations, including single-processor, multiprocessor or multi-coreprocessor computer systems, mini-computing devices, mainframe computers,as well as personal computers, hand-held computing devices (e.g.,personal digital assistant (PDA), phone, watch . . . ),microprocessor-based or programmable consumer or industrial electronics,and the like. The illustrated aspects can also be practiced indistributed computing environments where tasks are performed by remoteprocessing devices that are linked through a communications network.However, some, if not all aspects of the claimed subject matter can bepracticed on stand-alone computers. In a distributed computingenvironment, program modules can be located in both local and remotememory storage devices.

Referring now to FIG. 11, there is illustrated a schematic block diagramof a computing environment 1100 in accordance with the subjectspecification. The system 1100 includes one or more client(s) 1102. Theclient(s) 1102 can be hardware and/or software (e.g., threads,processes, computing devices). The client(s) 1102 can house cookie(s)and/or associated contextual information by employing the specification,for example.

The system 1100 also includes one or more server(s) 1104. The server(s)1104 can also be hardware and/or software (e.g., threads, processes,computing devices). The servers 1104 can house threads to performtransformations by employing the specification, for example. Onepossible communication between a client 1102 and a server 1104 can be inthe form of a data packet adapted to be transmitted between two or morecomputer processes. The data packet can include a cookie and/orassociated contextual information, for example. The system 1100 includesa communication framework 1106 (e.g., a global communication networksuch as the Internet) that can be employed to facilitate communicationsbetween the client(s) 1102 and the server(s) 1104.

Communications can be facilitated via a wired (including optical fiber)and/or wireless technology. The client(s) 1102 are operatively connectedto one or more client data store(s) 1108 that can be employed to storeinformation local to the client(s) 1102 (e.g., cookie(s) and/orassociated contextual information). Similarly, the server(s) 1104 areoperatively connected to one or more server data store(s) 1110 that canbe employed to store information local to the servers 1104.

Referring now to FIG. 12, there is illustrated a block diagram of acomputer operable to execute the disclosed architecture. In order toprovide additional context for various aspects of the subjectspecification, FIG. 12 and the following discussion are intended toprovide a brief, general description of a suitable computing environment1200 in which the various aspects of the specification can beimplemented. While the specification has been described above in thegeneral context of computer-executable instructions that can run on oneor more computers, those skilled in the art will recognize that thespecification also can be implemented in combination with other programmodules and/or as a combination of hardware and software.

Generally, program modules include routines, programs, components, datastructures, etc., that perform particular tasks or implement particularabstract data types. Moreover, those skilled in the art will appreciatethat the inventive methods can be practiced with other computer systemconfigurations, including single-processor or multiprocessor computersystems, minicomputers, mainframe computers, as well as personalcomputers, hand-held computing devices, microprocessor-based orprogrammable consumer electronics, and the like, each of which can beoperatively coupled to one or more associated devices.

The illustrated aspects of the specification can also be practiced indistributed computing environments where certain tasks are performed byremote processing devices that are linked through a communicationsnetwork. In a distributed computing environment, program modules can belocated in both local and remote memory storage devices.

A computer typically includes a variety of computer-readable media.Computer-readable media can be any available media that can be accessedby the computer and includes both volatile and nonvolatile media,removable and non-removable media. By way of example, and notlimitation, computer-readable media can comprise computer storage mediaand communication media. Computer storage media includes volatile andnonvolatile, removable and non-removable media implemented in any methodor technology for storage of information such as computer-readableinstructions, data structures, program modules or other data. Computerstorage media includes, but is not limited to, RAM, ROM, EEPROM, flashmemory or other memory technology, CD-ROM, digital versatile disk (DVD)or other optical disk storage, magnetic cassettes, magnetic tape,magnetic disk storage or other magnetic storage devices, or any othermedium which can be used to store the desired information and which canbe accessed by the computer.

Communication media typically embodies computer-readable instructions,data structures, program modules or other data in a modulated datasignal such as a carrier wave or other transport mechanism, and includesany information delivery media. The term “modulated data signal” means asignal that has one or more of its characteristics set or changed insuch a manner as to encode information in the signal. By way of example,and not limitation, communication media includes wired media such as awired network or direct-wired connection, and wireless media such asacoustic, RF, infrared and other wireless media. Combinations of the anyof the above should also be included within the scope ofcomputer-readable media.

With reference again to FIG. 12, the example environment 1200 forimplementing various aspects of the specification includes a computer1202, the computer 1202 including a processing unit 1204, a systemmemory 1206 and a system bus 1208. The system bus 1208 couples systemcomponents including, but not limited to, the system memory 1206 to theprocessing unit 1204. The processing unit 1204 can be any of variouscommercially available processors. Dual microprocessors and othermulti-processor architectures can also be employed as the processingunit 1204.

The system bus 1208 can be any of several types of bus structure thatcan further interconnect to a memory bus (with or without a memorycontroller), a peripheral bus, and a local bus using any of a variety ofcommercially available bus architectures. The system memory 1206includes read-only memory (ROM) 1210 and random access memory (RAM)1212. A basic input/output system (BIOS) is stored in a non-volatilememory 1210 such as ROM, EPROM, EEPROM, which BIOS contains the basicroutines that help to transfer information between elements within thecomputer 1202, such as during start-up. The RAM 1212 can also include ahigh-speed RAM such as static RAM for caching data.

The computer 1202 further includes an internal hard disk drive (HDD)1214 (e.g., EIDE, SATA), which internal hard disk drive 1214 can also beconfigured for external use in a suitable chassis (not shown), amagnetic floppy disk drive (FDD) 1216, (e.g., to read from or write to aremovable diskette 1218) and an optical disk drive 1220, (e.g., readinga CD-ROM disk 1222 or, to read from or write to other high capacityoptical media such as the DVD). The hard disk drive 1214, magnetic diskdrive 1216 and optical disk drive 1220 can be connected to the systembus 1208 by a hard disk drive interface 1224, a magnetic disk driveinterface 1226 and an optical drive interface 1228, respectively. Theinterface 1224 for external drive implementations includes at least oneor both of Universal Serial Bus (USB) and IEEE 1394 interfacetechnologies. Other external drive connection technologies are withincontemplation of the subject specification.

The drives and their associated computer-readable media providenonvolatile storage of data, data structures, computer-executableinstructions, and so forth. For the computer 1202, the drives and mediaaccommodate the storage of any data in a suitable digital format.Although the description of computer-readable media above refers to aHDD, a removable magnetic diskette, and a removable optical media suchas a CD or DVD, it should be appreciated by those skilled in the artthat other types of media which are readable by a computer, such as zipdrives, magnetic cassettes, flash memory cards, cartridges, and thelike, can also be used in the example operating environment, andfurther, that any such media can contain computer-executableinstructions for performing the methods of the specification.

A number of program modules can be stored in the drives and RAM 1212,including an operating system 1230, one or more application programs1232, other program modules 1234 and program data 1236. All or portionsof the operating system, applications, modules, and/or data can also becached in the RAM 1212. It is appreciated that the specification can beimplemented with various commercially available operating systems orcombinations of operating systems.

A user can enter commands and information into the computer 1202 throughone or more wired/wireless input devices, e.g., a keyboard 1238 and apointing device, such as a mouse 1240. Other input devices (not shown)can include a microphone, an IR remote control, a joystick, a game pad,a stylus pen, touch screen, or the like. These and other input devicesare often connected to the processing unit 1204 through an input deviceinterface 1242 that is coupled to the system bus 1208, but can beconnected by other interfaces, such as a parallel port, an IEEE 1394serial port, a game port, a USB port, an IR interface, etc.

A monitor 1244 or other type of display device is also connected to thesystem bus 1208 via an interface, such as a video adapter 1246. Inaddition to the monitor 1244, a computer typically includes otherperipheral output devices (not shown), such as speakers, printers, etc.

The computer 1202 can operate in a networked environment using logicalconnections via wired and/or wireless communications to one or moreremote computers, such as a remote computer(s) 1248. The remotecomputer(s) 1248 can be a workstation, a server computer, a router, apersonal computer, portable computer, microprocessor-based entertainmentappliance, a peer device or other common network node, and typicallyincludes many or all of the elements described relative to the computer1202, although, for purposes of brevity, only a memory/storage device1250 is illustrated. The logical connections depicted includewired/wireless connectivity to a local area network (LAN) 1252 and/orlarger networks, e.g., a wide area network (WAN) 1254. Such LAN and WANnetworking environments are commonplace in offices and companies, andfacilitate enterprise-wide computer networks, such as intranets, all ofwhich can connect to a global communications network, e.g., theInternet.

When used in a LAN networking environment, the computer 1202 isconnected to the local network 1252 through a wired and/or wirelesscommunication network interface or adapter 1256. The adapter 1256 canfacilitate wired or wireless communication to the LAN 1252, which canalso include a wireless access point disposed thereon for communicatingwith the wireless adapter 1256.

When used in a WAN networking environment, the computer 1202 can includea modem 1258, or is connected to a communications server on the WAN1254, or has other means for establishing communications over the WAN1254, such as by way of the Internet. The modem 1258, which can beinternal or external and a wired or wireless device, is connected to thesystem bus 1208 via the serial port interface 1242. In a networkedenvironment, program modules depicted relative to the computer 1202, orportions thereof, can be stored in the remote memory/storage device1250. It will be appreciated that the network connections shown areexample and other means of establishing a communications link betweenthe computers can be used.

The computer 1202 is operable to communicate with any wireless devicesor entities operatively disposed in wireless communication, e.g., aprinter, scanner, desktop and/or portable computer, portable dataassistant, communications satellite, any piece of equipment or locationassociated with a wirelessly detectable tag (e.g., a kiosk, news stand,restroom), and telephone. This includes at least Wi-Fi and Bluetooth™wireless technologies. Thus, the communication can be a predefinedstructure as with a conventional network or simply an ad hoccommunication between at least two devices.

Wi-Fi, or Wireless Fidelity, allows connection to the Internet from acouch at home, a bed in a hotel room, or a conference room at work,without wires. Wi-Fi is a wireless technology similar to that used in acell phone that enables such devices, e.g., computers, to send andreceive data indoors and out; anywhere within the range of a basestation. Wi-Fi networks use radio technologies called IEEE 802.11 (a, b,g, etc.) to provide secure, reliable, fast wireless connectivity. AWi-Fi network can be used to connect computers to each other, to theInternet, and to wired networks (which use IEEE 802.3 or Ethernet).Wi-Fi networks operate in the unlicensed 2.4 and 5 GHz radio bands, atan 11 Mbps (802.11a) or 54 Mbps (802.11b) data rate, for example, orwith products that contain both bands (dual band), so the networks canprovide real-world performance similar to the basic 10BaseT wiredEthernet networks used in many offices.

What has been described above includes examples of the subjectspecification. It is, of course, not possible to describe everyconceivable combination of components or methodologies for purposes ofdescribing the subject specification, but one of ordinary skill in theart can recognize that many further combinations and permutations of thesubject specification are possible. Accordingly, the subjectspecification is intended to embrace all such alterations, modificationsand variations that fall within the spirit and scope of the appendedclaims. Furthermore, to the extent that the term “includes” is used ineither the detailed description or the claims, such term is intended tobe inclusive in a manner similar to the term “comprising” as“comprising” is interpreted when employed as a transitional word in aclaim.

What is claimed is:
 1. A computer-implemented method for providinggesture-based input to an application user interface, comprising:associating a floating tool palette with the application user interface,the floating tool palette including at least one gestural tip thatpresents gesture functionality associated with the application userinterface based at least in part on a period of time between a currentinteraction of a user with a particular element of the application userinterface and a previous interaction of the user with the particularelement, wherein the at least one gestural tip illustrates movement of aparticular gesture sequence, and wherein the at least one gestural tipcomprises a video or an animation of the particular gesture sequence;capturing at least one gesture input in response to presentation of theat least one gestural tip, wherein the at least one gesture input isassociated with the at least one gestural tip included in the floatingtool palette; and based at least in part on the captured at least onegesture input, forwarding event data to an application associated withthe application user interface.
 2. The method of claim 1, furthercomprising generating the event data based at least in part on thecaptured at least one gesture input.
 3. The method of claim 1, whereinthe floating tool palette comprises a translucent overlay placed on theapplication user interface.
 4. The method of claim 3, further comprisingdisplaying the floating tool palette as opaque when a user input hoversover the floating tool palette.
 5. The method of claim 1, furthercomprising providing the floating tool palette based at least in part ona user preference persisted in a data store.
 6. The method of claim 1,wherein the at least one gestural tip presents gesture functionalitybased at least partly on at least one detected non-gesture input to thefloating tool palette.
 7. The method of claim 1, further comprisingproviding the floating tool palette with a subset of the gestural tipsthe floating tool palette is configured to display.
 8. The method ofclaim 1, wherein at least one of: the at least one gesture inputcomprises at least one of a gesture start point, a gesture end point, apath of a gesture movement, or a speed of motion of a gesture movement;or the at least one gesture input includes a scrolling gesture, andwherein the event data includes scrolling event data.
 9. One or morecomputer-readable storage media storing instructions that, when executedby at least one processor, instruct the at least one processor toperform actions comprising: providing a tool palette for a userinterface of an application, the tool palette including gestural tipsthat are provided based at least partly on a period of time between acurrent interaction of a user with a particular element of theapplication user interface and a previous interaction of the user withthe particular element, wherein each of the gestural tips illustratesmovement of a respective gesture sequence, and wherein each of thegestural tips comprises a video or an animation of the respectivegesture sequence; capturing at least one gesture associated with thegestural tips in response to presentation of at least one of thegestural tips, wherein the at least one gesture is input at least partlyto the tool palette; and forwarding event data to the application, theevent data generated based at least partly on the captured at least onegesture.
 10. The one or more computer-readable storage media of claim 9,wherein the tool palette comprises a translucent overlay to the userinterface.
 11. The one or more computer-readable storage media of claim10, wherein the actions further comprise solidifying the tool palettewhen an input hovers over the tool palette.
 12. The one or morecomputer-readable storage media of claim 9, wherein the tool paletteprovides support for one or more gesture-based commands in the userinterface of the application, wherein the application was not originallyimplemented to support gesture-based commands.
 13. The one or morecomputer-readable storage media of claim 9, wherein the at least onegesture is initiated within the tool palette and is terminated outsidethe tool palette.
 14. A system comprising: at least one processor; anintelligence component comprising instructions executed by the at leastone processor to infer an unfamiliarity of a user with an element of auser interface for an application, the inferring based at least partlyon a period of time between a current interaction of the user with theelement and a previous interaction of the user with the element; adecision component comprising instructions executed by the at least oneprocessor to provide a tool palette that includes gestural tips for theuser interface, the gestural tips based at least partly on theinferring, wherein each of the gestural tips illustrates movement of arespective gesture sequence, and wherein each of the gesture tipscomprises a video or an animation of the respective gesture sequence;and an interface component comprising instructions executed by the atleast one processor to: capture at least one gesture associated with thegestural tips in response to presentation of at least one of thegestural tips, wherein the at least one gesture is input at least partlyto the tool palette; generate event data based at least partly on thecaptured at least one gesture; and forward the generated event data tothe application.
 15. The system of claim 14, wherein the tool palettecomprises a translucent overlay to the user interface.
 16. The system ofclaim 15, wherein the interface component further operates to solidifythe tool palette as a user input hovers over the tool palette.
 17. Thesystem of claim 14, wherein the tool palette provides support for one ormore gesture-based commands in the user interface of the application,wherein the application was not originally implemented to support theone or more gesture-based commands.
 18. The system of claim 14, whereinthe at least one gesture is initiated within the tool palette and isterminated outside the tool palette.
 19. The system of claim 14, whereinthe at least one gesture includes a scrolling gesture, and wherein theevent data includes scrolling event data.